I am deleting the attribute and associated type from my DOORS module. The attribute and type is getting deleted but the history is logged as "Read locked data". I do not want these kinds of log in the history. Please elaborate the reason and the way to delete so that this log can be avoided.
Thanks. Rakesh Lal - Wed Jan 08 08:06:22 EST 2014 |
Re: Read Locked Data They figure if someone lacks even "R" access to the attribute then they must also be denied seeing History for that attribute and that is called "Read Locked".. That makes sense. However they implemented it funny. If the attribute doesn't exist at all then nobody has even "R" access and everybody therefore cannot see the History. Well except of course the super-user "Administrator" can see all History regardless. Note that the attribute "doesn't exist" anymore if you deleted or renamed it. If you cannot log in as the "Administrator" then I suppose you could Edit the module, re-create the attribute (by it's old name), view History, then close without saving. Yuuuck. You could also have your own private database where you DO have the "Administrator" password; archive the module, restore it locally, and peek at its History there. Also Yuuuck. -Louie I proposed and was rejected the idea that a module-admin with RMCDA access should be able to see all History. |